Looks good! Do we know if the way screen readers read these attributes is generic enough to be on Widget?

I went back and forth with this question before I made the PR and I was hoping you would be the tie breaker. But honestly, there are no generics with the screen reader. If aria-hidden, it's not communicated. If aria-disabled, its announced as such and it cannot be interacted with. There is not much left to the developer to decided, as in the case with the CSS needed to support these states. If the classes are meant to support/ communicate state, then we really need to provide the same to AT. There is also the potential conflict between the focused and disabled state, as disabled elements may not be focusable, but that is a different conversation.

That's what I was expecting to hear. 👍 from my side.